How to use DXL code to open module for unmanaged change

Currently, the module is under control(integrating with Change or RTC). We wanna modify values of some unmanaged attributes via DXL. So we are thinking to open the module for unmanaged changes via code and do the changes. But there is no document about how to load module for unmanaged changes by DXL. Actually, this question is same with https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014587605&ps=25  where it does not have the expected answer.

Re: How to use DXL code to open module for unmanaged change
DOORSHAM - Tue Nov 15 16:19:24 EST 2016

Concept of managed / unmanaged change is not a doors concept -- it is a by product of users imagination

Re: How to use DXL code to open module for unmanaged change
Mike.Scharnow - Tue Nov 15 18:10:23 EST 2016

@DOORSHAM 5c843324-bbb9-47c0-8e6d-48992ddaca3c: sometimes I do not understand your comments. Why should Change control and the difference between managed and unmanaged attributes and edit mode not be a concept of DOORS? Admittedly, it has not been part of DOORS in the first versions and is realized as an add-on, but this is true for many parts of DOORS.

@XiaoXingLu 3cdc37d5-edc8-42ad-b265-22e430acba5c​: It depends on what you want to do with the module. If you have a script which opens a module, changes some values and then saves and closes the module again, e.g. as part of a bigger script, it should be possible, if I remember correctly, to open the module in edit mode, but invisibly (second parameter of edit command must be "false"). In this case, the post open module trigger should allow editing without any popups.

Hope this helps,
Mike

Re: How to use DXL code to open module for unmanaged change
XiaoXingLu - Thu Nov 17 00:34:56 EST 2016

Thanks Mike, I try below, which is a simple dxl to open module "M1" and set the attribute value of "okay" of object with absolute number "1" to be "example value":

----------------------------------------------

Module m= edit("/Rational DOORS-Change Interface/M1",false)

Object o=gotoObject(1,m)

o."okay"="example value"

----------------------------------------------

Then I get below message:

---------------------------------------------

-R-W- DXL: <Line:5> no access to modify attribute 'okay'

---------------------------------------------

But obviously, this user has permission to modify the value of 'okay'. So I think the module is opened as read-only mode if the module is turned on CM.

While on another module without CM turn on, the similar code can set the attribute value without problem.

So my question would be, if the module is turned on CM, how to write code to open the module and edit value of those unmanaged attributes?

Re: How to use DXL code to open module for unmanaged change
Mike.Scharnow - Thu Nov 17 03:45:18 EST 2016

I don't have a live system with Change enabled at the moment, so I cannot check it directly.

Some ideas:

Did you enable Debugging and check the log?

To ensure whether it is a problem with edit mode or access right: 

- check the result of the "edit" command by evaluating isEdit()

If you log into DOORS as "Administrator", is there any difference?

If the module is in edit mode after opening, the message "no access to modify attribute" is rather strange, as the bridge, if I remember correctly, does not prevent users from changing attributes. Are you sure that "okay" is an object attribute and that the user has write access?

The DOORS 2 Change Bridge works using triggers. When the edit command has been successful, there should be no trigger installed.

So check for existing triggers after the edit command 

Trigger t
for t in m do { print name t "\n" }

BTW:  which DOORS version are you using? Perhaps in older versions, it was not possible to bypass the edit trigger in invisible mode. Perhaps you can open a Service Request with IBM and ask them directly?

Re: How to use DXL code to open module for unmanaged change
DOORSHAM - Sat Nov 26 08:06:05 EST 2016

No one expects you to understand.

Certainly no one can expect you to rise above your own level of comprehension.

Re: How to use DXL code to open module for unmanaged change
Mathias Mamsch - Sat Nov 26 13:55:22 EST 2016

Sorry, DOORSHAM but you answer is like a lot of your answers not helpful and neither directly adressing the question of Mike nor the poster's. I am not sure, if by answers like these you just want to increase you post-count but maybe you simply go and find some other place to insult users who try to help others or try to help you to recognize the uselessness of your answer.  Just my two cents :-) Sorry for posting of topic.

Re: How to use DXL code to open module for unmanaged change
DOORSHAM - Sat Nov 26 16:28:48 EST 2016

I take it now that you own this website and have control of it -- does ibm agree with your being in charge,

Both you and Mike initiate an attack on me -- looks like you both lake the moral integrity to be allowed to roam the web  with out picking fights.  

Re: How to use DXL code to open module for unmanaged change
PekkaMakinen - Sun Nov 27 06:21:32 EST 2016

Re: How to use DXL code to open module for unmanaged change
Bill_B. - Thu Dec 01 13:40:13 EST 2016

DOORSHAM;

I do not believe anyone (especially Mike, Mathias, or other well respected, long time aides to this and other sites) is attacking you merely asking you to address the issues of the poster and stop with the nonsense/non-answer wise cracks that no one seems to find funny but you...I personally note/grimace and try to skip anything you post to these sites as they are normally nonsense/non-answers and insults to the poster for not knowing the answer to the question they are posting...as was stated above...my 2 cents...

Re: How to use DXL code to open module for unmanaged change
XiaoXingLu - Mon Jan 09 22:26:41 EST 2017

Actually, I am a DOORS L2 support. Initially, I expected to get answer from here since I did not get any answer from my knowledge base. Later, I have escalated internally and got below answer, incase someone is seeking for same information:

---------------------------------------------------------------------

I can't really see a sensible way to implement this. Any suggestion I have would be limited by user type, and use potentially dangerous DXL (in addition to my previous concern).

Arguably the integration should have an API allowing this, but currently it doesn't.

As a workaround, how about running the DXL as a Database Manager user with the "-noTriggers" command line switch? That would allow all modifications, it wouldn't discard changes to managed attributes.

---------------------------------------------------------------------

So to be summarised, DOORS does not support API to implement it. As a workaround, we can use -noTriggers to disable all triggers and modify the value of the attributes(including managed and unmanaged attribute, that is the risk we can see.).

Thanks all. ​